Comments
-
Nobody responded to my plea for help. I give up. I'll spin up a pair of Windows Servers running Routing and Remote Access Services (RRAS) to create the tunnel.
-
Fixed typos: I would expect to have to create an IPv6 route to reach fd00:1ac:1::/64 via the Sonicwall's X1 (LAN) interface (fd00:1ac:5::ff/64 -> fd00:1ac:1::ff/64 via gateway fd00:1ac:5::fd) for PCs on the LAN. I pinged from from High Point to fd00:1ac:1::fd and got a reply.
-
The other weird thing was the source address on the ICMPv6 Ping Reply (Type 129). The SonicWall at Highpoint has X1 (LAN) fd00:1ac:1::ff, with its counterpart in Raleigh having fd00:1ac:5::ff. I pinged from HighPoint to fd00:1ac:5::fd and got a reply, which was wrongly dropped per policy as I explained above. The weird…
-
I am making progress. I can now ping IPv6 from fd00:1ac:5::/64 (High Point NC) to fd00:1ac:1::/64 (Raleigh) through an IPv4 GRE tunnel. The return pings are getting dropped by policy despite a wildcard access rule allowing it. It turns out that you can create a 6to4 interface for a an IPv4 GRE tunnel for IPv6 packets. It…
-
Can anybody confirm if the SonicWall allows IPv6 to be tunneled through an IPv4 site-to-site VPN? The documentation says it can be done. Page 6 of the SonicOS 7and SonicOSX 7 IPSec VPN Administration Guide says, VPNs can support either remote access—connecting a user’s computer to a corporate network—or site to site, which…